-
Notifications
You must be signed in to change notification settings - Fork 288
Init: DEX MCP Server #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| @@ -0,0 +1,47 @@ | |||
| import { fetchCloudflareApi } from '@repo/mcp-common/src/cloudflare-api' | |||
|
|
|||
| export const fetchDexTestAnalyzation = async ({ | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Confused why CI didn't run on this PR, wonder if it's because it came from a fork? |
Yeah, I enabled that setting. We have to manually run CI on forks because the evals job has some secrets. |
| export type State = { activeAccountId: string | null } | ||
|
|
||
| export class MyMCP extends McpAgent<Env, State, Props> { | ||
| server = new McpServer({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to get metrics/error tracking on all of our MCP servers, I added a utility class in a recent PR here: #69
I’ll write up a quick guide on how to use this tomorrow
Doesn’t need to be this PR, but we should use that McpServer wrapper before deploying this


WIP: Would like a review by the team with feedback on any structural issues.